Hi, thanks for the issue report and the PR! It's still not clear to me what the best solution for this problem is so I'll keep investigating this.

I don't think the solution implemented in this PR is good enough because it basically modifies the data that is being read so the user will not actually be able to read the correct data from the database.

Since the type itself does not support the values that are being read from the database it seems to me that we have 2 options:

1. Introduce a breaking change and change the default C# type that is associated with this C* type
2. Introduce a custom serializer that users can use if they run into this issue (and potentially set this as the default in the next major version of the driver, whenever that happens)

I'm going to discard option 1 because this issue is very very rare so I can't justify forcing all users to change their application code for something that doesn't affect the vast majority of the userbase. For context, this is the first report of this issue and the driver has been around for a long time.

I'll try to get something together for option 2 to see if it is a good solution for this.

i guess, the best way to fix it is fix the datetime lib in java :D
even if we fix it, it won't work old incorrect data.

we are using csharpdriver with json select, and then deserialize to entity object with external json lib(newtonsoft etc.).
therefore we prevented that DateTimeSerialization throws exception by not using.
maybe, new serializer that handle this issue would be good.

if i have time, i am gonna look at what i can do better on this problem than this.